home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19970104-19970326
/
000391_news@columbia.edu _Mon Mar 10 10:48:27 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id KAA07393
for <kermit.misc@watsun.cc.columbia.edu>; Mon, 10 Mar 1997 10:48:26 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id KAA03755
for kermit.misc@watsun; Mon, 10 Mar 1997 10:48:26 -0500 (EST)
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Help to read file...
Date: 10 Mar 1997 15:48:25 GMT
Organization: Columbia University
Lines: 32
Message-ID: <5g1ag9$pue$1@apakabar.cc.columbia.edu>
References: <5f2ove$4sb@tom.pppl.gov> <5f4l8u$7ao$1@apakabar.cc.columbia.edu> <5f6479$sdq$1@brokaw.wa.com> <5fto4c$ms2@tom.pppl.gov>
NNTP-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:6725
In article <5fto4c$ms2@tom.pppl.gov>,
augusto rousset <arousset@true.net> wrote:
: I want to thank Frank and Ken for their help, tough this wasn't a
: kermit question. I have not enough knowledge of all this encoding
: matters, and i'm still trying to solve this problem.
: �Could you tell me what a C compiler is?
: I've been looking other postings in this newsgroup and saw the
: announcement of MS Kermit for DOS. �Can't this program
: help me to view the kind of file I want?
:
Kermit is (among other things) a terminal emulator, not an email or
MIME client. Just because you are using Kermit to "read email" does
not mean Kermit understands every conceivable encoding that people
use when sending you email, any more than a real terminal would (in
case you don't know what a terminal is, it is sort of like a
typewriter).
The "MIME revolution" has, in my opinion, perhaps done more harm
than good, by creating the expectation that you can send anything to
anybody and they will be able to read it. How many of us receive
(for example) Microsoft Word 7.0 documents encoded by btoa, when
our email client (a) does not reside on a Microsoft OS, and (b) does
not have a btoa decoder?
People who are new to computing or "the net" have no idea that this
would be a problem and tend not to understand the explanation when
they are told that it is. "Please resend your message in plain
text," we ask, and they ask, "What is plain text?"
It will only get worse.
- Frank